Synchronized media capturing for an interactive scene

ABSTRACT

There are provided systems and methods for synchronized media capturing for an interactive scene. A user at a venue may watch an event unfold at the venue. The venue may include wireless beacons established throughout the venue. The wireless beacons may be configured to establish short range wireless communications with the user&#39;s device. Once a connection is established, the wireless beacons may instruct the user&#39;s device to capture media of an instance during the event. The wireless beacons may similar instruct other user&#39;s devices to capture media of the instance at the same time, thereby synchronizing media capturing of a particular instance during the event. The user may review the media and select to delete the media or upload the media to a media sharing service. The server may further process the media into an interactive scene.

TECHNICAL FIELD

The present application generally relates to synchronized mediacapturing for an interactive scene and more specifically to utilizingwireless beacons at a location where an event is occurring to issue acommand to multiple users' device cameras at the scene that synchronizesthe cameras to capture media of the event from different perspectives.

BACKGROUND

Users may attend events, such as sporting games, concerts, liveperformances, or other organized events. At these events, these usersmay bring user devices, such as mobile phones, tablet computers, anddigital cameras. The users may utilize these user devices to captureimages during the events, such as when an artist comes on stage toperform a song, an exciting play occurs within a sports game, etc. Withthe prevalence of social media and social networking services, theseusers may upload the images they capture to a service, which may thenshare the images with friends and family the user has added to theirnetwork. However, images of these instances in the event may be taken atdifferent times and aimed at different parts of the venue. Thus, otherusers viewing the images online may not view a complete picture of aparticularly exciting instance during the event. Further, users whoattend the event usually may only access images they captured and imagesthat their friends and family captured at the event. Thus, the user maybe prevented from viewing other perspectives of the image or a moreinteractive scene of the event.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a networked system suitable forimplementing the processes described herein, according to an embodiment;

FIG. 2 is an exemplary environment including a plurality of userscapturing synchronized media of an instance during an event for usecreating an interactive scene, according to an embodiment;

FIG. 3 is an exemplary system environment including a server preparingan interactive scene from synchronized media submitted by user devices,according to an embodiment;

FIG. 4 is a flowchart of an exemplary process for synchronized mediacapturing for an interactive scene, according to an embodiment; and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

Provided are methods that provide synchronized image capturing for aninteractive scene. Systems suitable for practicing methods of thepresent disclosure are also provided.

Various locations may provide short range wireless communications with adevice, such as through WiFi, Bluetooth Low Energy (BLE), LTE Direct, orother communication protocol. These beacons may be set up at a locationand communicate with devices to alert users of check-in services throughtheir device. The beacons may provide additional functionality, such asestablishing a connection with a device and/or server to engage intransactions, complete communications, and execute processes. Thebeacons may provide communications to the devices directly, includinginformation stored in the beacons. The beacons may also providecommunication with a device at a venue and/or a server of a serviceprovider for that venue.

A location for an event (e.g., a venue hosting a sports game, concert,etc.) may offer check-in services to users utilizing wireless beaconsthroughout the location. These short range wireless beacons at thelocation may be configured to communicate with a device for the users atthe location. For example, the short range wireless beacon may beestablished throughout grandstands, seating areas, concession areas,dance floors, entryways, etc., at the location. The beacons may employBLE, LTE Direct, etc., communications that emit a signal receivable bythe devices of the users. The communication may include an identifierfor the beacon, the user, the venue's devices/services, and/or a serviceprovider for the venue.

The devices for the users may be set up to passively monitor forcommunications from the beacons. When a device detects the signal andverifies the one or more identifiers from a beacon, both the device andthe beacon may ramp up in power and establish a connection, where theconnection may further enable the device to communicate with the beacon,the venue's devices/servers, and/or the service provider. The beacon maybe connected to a networked device at the location, or the beacon mayinclude network functionality to communicate with other devices and/orservers. Thus, the beacon enables the user's device to establish aconnection, communicate check-in information (e.g., an identifier forthe user), and/or initiate a check-in with the location and the specificbeacon initiating the connection. The check-in may be completedautomatically when the user's device is in range of the beacon, or maybe completed after prompting the user to check-in when the user's deviceis in range of the beacon.

The location for the event may establish a plurality of wireless beaconsthroughout the location, as previously discussed. The wireless beaconsmay further be connected to a device or server (e.g., a venues server ora service provider for the venue). The device or server for the locationmay determine when an instance in the event occurs or is going to occur(e.g., when a play occurs or is about to occur in a sports game, when amusician comes on stage or is about it come on stage in a concert,etc.). The device or server may determine the upcoming or currentoccurrence of the instance based on devices in connection with thedevice/server, such as cameras, microphones, etc., or if the instance isplanned, may receive previous input for a time of the instance. Inaddition to the timing of the instance, the device/server may determinea location, orientation, coordinates, or other direction parameter forwhere the instance is taking place or will take place.

Based on determining an instance in the event, the device/server mayinstruct the wireless beacons to issue a request or command to userdevices held by the audience in proximity to each of the wirelessbeacons. This request or command may correspond to a request or commandto capture an image of the instance when the instance occurs. Thus, theuser devices for the audience members may be synchronized to captureimages of the instance at the same time using the wireless beacons. Inaddition to the request/command, the wireless beacons may instructionthe audience members where to point or direct a camera of the userdevices. The instruction may include directional information thatassists the user in aiming the camera. Additionally, the request/commandmay prevent the camera from being used prior to the instance. Forexample, concerts, sports games, etc., may prevent photography and/orflash photography up to a certain point during the event. Thus, therequest/command may prevent camera usage prior to the instance, whereoccurrence of the instance causes an image to be captured and enablesuse of the camera again. If the instance does not occur after a periodof time the user devices may again capture images. However, the userdevice cameras may also be prevented from capturing images after theinstance or even if the instance does not occur if photography isprevented during the event except for at a predetermined instance.Although it is presently discussed that the request/command may be tocapture an image of the instance, the request/command may correspond toa request/command to capture any media, including video, audio, andaudiovisual media.

Once the image of the event is captured, the image may be displayed tothe audience member having the user device. The audience member may thenchoose to upload the image to a service provider or delete the image. Ifthe audience member uploads the image to the service provider, theservice provider may utilize the image with other images of the sameinstance to generate an interactive scene of the instance during theevent. The interactive scene may enable users (e.g., the audiencemembers, friends, family, or other people in the event or producing theevent) to view the instance in the event through multiple perspectives.The users may scroll through multiple images captured of the instancefrom the multiple perspectives. In further embodiments, an interactivescene may be built that allows the users to pan, rotate, zoom, andchange a view of the instance. Moreover, the service provider may offersales of the interactive scene or images of the instance to the users.

FIG. 1 is a block diagram of a networked system 100 suitable forimplementing the processes described herein, according to an embodiment.As shown, system 100 may comprise or implement a plurality of devices,servers, and/or software components that operate to perform variousmethodologies in accordance with the described embodiments. Exemplarydevice and servers may include device, stand-alone, and enterprise-classservers, operating an OS such as a MICROSOFT® OS, a UNIX® OS, a LINUX®OS, or other suitable device and/or server based OS. It can beappreciated that the devices and/or servers illustrated in FIG. 1 may bedeployed in other ways and that the operations performed and/or theservices provided by such devices and/or servers may be combined orseparated for a given embodiment and may be performed by a greaternumber or fewer number of devices and/or servers. One or more devicesand/or servers may be operated and/or maintained by the same ordifferent entities.

System 100 includes a user 102, a user device 110, a venue 140, andimage processing server 150 in communication over a network 160. User102, such as an audience member, fan, or other viewer of an event, mayarrive at venue 140 to watch the event with user device 110. Venue 140includes wireless beacons 146 established throughout venue 140 andconfigured to connect to user device 110. Once user device 110establishes a connection with one or more of wireless beacons 146 atvenue 140, the one or more wireless beacons 146 may then instruct user102 to point a device camera 130 of user device 110 at an instanceoccurring in the event and send a command to user device 110 to capturean image of the instance. The image may then be transmitted to imageprocessing server 150 for processing and incorporation in an interactivescene.

User device 110, wireless beacons 146, and image processing server 150may each include one or more processors, memories, and other appropriatecomponents for executing instructions such as program code and/or datastored on one or more computer readable mediums to implement the variousapplications, data, and steps described herein. For example, suchinstructions may be stored in one or more computer readable media suchas memories or data storage devices internal and/or external to variouscomponents of system 100, and/or accessible over network 160.

User device 110 may be implemented using any appropriate hardware andsoftware configured for wired and/or wireless communication withwireless beacons 146 and/or image processing server 150. For example, inone embodiment, user device 110 may be implemented as a personalcomputer (PC), a smart phone, laptop computer, wristwatch withappropriate computer hardware resources, eyeglasses with appropriatecomputer hardware (e.g. GOOGLE GLASS®) and/or other types of computingdevices capable of transmitting and/or receiving data, such as an IPAD®from APPLE®. Although a user device is shown, the user device may bemanaged or controlled by any suitable processing device. Although onlyone user device is shown, a plurality of user devices may functionsimilarly.

User device 110 of FIG. 1 contains a check-in application 112, a cameraapplication 120, a device camera 130, other applications 114, a database116, and a communication module 118. Check-in application 112, cameraapplication 120, and other applications 114 may correspond to processes,procedures, and/or applications executable by a hardware processor, forexample, a software program. In other embodiments, user device 110 mayinclude additional or different software as required.

Check-in application 112 may be used by user 102 of user device 110 toestablish a connection with one or more of wireless beacons 146,including a check-in with venue 140. Check-in application 112 maycorrespond to a specific application utilized by user device 110 withvenue 140 to complete a check-in for venue 140. The check-in with venue140 may correspond to a process to log in to a user account of user 102with venue 140 (or image processing server 150 if image processingserver 150 provides check-in services). In other embodiments, thecheck-in may provide and/or verify the identity of user 102, includingtransmission of an identifier for user 102 and/or user device 110. Thecheck-in may be completed over network 160 with venue 140. In suchembodiments, check-in application 112 may correspond more generally to abrowser application configured to communicate with venue 140.

Check-in application 112 may also receive short range wirelesscommunications from wireless beacons 146 at a location for one or moreof wireless beacons 146 and transmit information to wireless beacons146, including check-in information for a check-in process with venue140 (or image processing server 150 if image processing server 150provides check-in services) that associates user 102 with the locationcorresponding to the one or more of wireless beacons 146 transmittingthe short range wireless communications. For example, the location forone of wireless beacons 146 may correspond to a seating, concessionareas, grandstands, theater/amphitheater locations, etc., in venue 140.In such an example, wireless beacons 146 may be range limited tocorrespond only to an area around the location for the one of wirelessbeacons 145. Wireless beacons 146 may be set to be range limited throughsignal strength of wireless beacons 146, or may be limited by virtue ofwalls, pillars, radiation absorbent materials, or other signalinterferences of venue 140. In response to a received identifier fromone or more of wireless beacons 146, check-in application 112 maytransmit information to one or more of wireless beacons 146 when user102 is nearby the one or more of wireless beacons 146 (e.g., sitting inarea G, mezzanine of a concert hall) enabling venue 140 to determine theposition of user 102 within venue 140 through wireless beacons 146. Oncecheck-in application 112 has connected to one or more of wirelessbeacons 146, check-in application 146 may begin transmitting informationbetween user device 110 and the connected beacons of wireless beacons146.

Check-in application 112 may execute in the background of an operatingsystem of user device 110 and be configured to establish connections,using communication module 118 of user device 110, with one or more ofwireless beacons 146. The connection may be established with or withoutuser input from user 102. For example, wireless beacons 146 maybroadcast a token, such as a universally unique identifier (UUID), forreception by check-in application 112, as will be explained in moredetail herein. Check-in application 112 may utilize communication module118 of user device 110 to receive the token from one or more of wirelessbeacons 146. If check-in application 112 acknowledges the UUID asidentifying wireless beacons 146, venue 140, and/or image processingserver 150 (e.g., if check-in application 112 determines the UUIDcorresponds to a request to complete a check-in), check-in application112 may transmit an identifier corresponding to user 102 and/or userdevice 110 back to the one or more of wireless beacons 146 transmittingthe UUID.

Check-in application 112 may utilize communication module 118 of userdevice 110 to communicate with wireless beacons 146 (e.g., over nearfield communication, Bluetooth, Bluetooth Low Energy, radio, infrared,LTE Direct, or other connection). The identifier from user device 110may include, be transmitted with, concatenated with, or otherwisebundled with the identifier received from wireless beacons 146. In otherembodiments, additional or different information may be transmitted towireless beacons 146, such as a name or other personal information foruser 102, and/or information for an account, event ticket, imagetracking number, etc. Moreover, the information transmitted to wirelessbeacons 146 does not need to be utilized to process and/or complete acheck-in in all embodiments.

Once a connection is established with wireless beacons 146, user device110 may be checked-in with venue 140 if user 102 has not previously beenchecked-in. The check-in process may also associate user 102 with theone or more of wireless beacons 146 used to connect to user device 110.For example, venue 140 may previously have registered wireless beacons146 as located in a specific area of venue 140 (e.g., grandstands,theater/amphitheater seating, etc.). Thus, venue 140 is informed thatuser 102 is at the specific area because user device 110 connects to theone or more wireless beacons 146 for that area. As previously discussed,in other embodiments, a check-in need not be processed and/or completedto associate user 102 with the area. Thus, other connections and datatransfers to the one or more wireless beacons 146 at the specific areamay be sufficient to associate user 102 with the specific area.

Once connected to one or more of wireless beacons 146, check-inapplication 112 may send and receive information with the connected oneor more of wireless beacons 146. Information received from a connectedbeacon of wireless beacons 146 may include a request/command to capturean instance during an event happening at venue 140. For example, anevent may correspond to a baseball game, concert, speech, etc. Thus, aninstance during the event may correspond to a homerun hit, a song orsolo by a musician, or an impactful statement during the speech,respectively. Venue 140 and/or image processing server 150 may determinewhen the instance occurs or when an instance is going to occur, as willbe explained in more detail herein. Once that determination is made, oneor more of wireless beacons 146 may issue the request/command to userdevice 110. Check-in application 112 may receive the request/command andmay instruct camera application 120 accordingly.

The request/command may also include prevent camera application 120 anddevice camera 130 from capturing images prior to the occurrence of theinstance. Thus, check-in application 112 may also issue an instructionto prevent the use of camera application 120 and device camera 130 priorto the instance. Check-in application 112 may release camera application120 and device camera 130 to begin capturing images again once theinstance has occurred, if sufficient time has occurred for the instanceto pass, or based on a time limit set by venue 140 and/or imageprocessing server 150 (e.g., if the instance does not occur and after aperiod of time, thereby insuring camera application 120 and devicecamera 130 does not remain locked). Thus, check-in application 112 mayenable image and video photography to again occur on user device 110even if the instance does not occur.

The prevention may insure that camera application 120 and device camera130 are available for capturing the image of the instance at the samemoment as other devices/camera at venue 140, thereby only preventingcamera application 120 and device camera 130 for capturing images for asmall time frame prior to the instance. However, other embodiments mayrequire the prevention to be issued well before the instance, such as inthe case of a dark exhibit, concert hall, during a pivotal sports playor action, etc. Thus, in such embodiments, the command/request tocapture the image may occur at some time prior to the instance whenphotography of the event should discontinue and prevent capturing ofimages up until the instance occurs during the event.

The request/command received by check-in application 112 may be issuedin one, two, or more steps. For example, in a two-step approach,check-in application 112 may receive a first request to capture an imageof an upcoming instance. The request may notify user 102 that aninstance during an event for capturing an image is upcoming and giveuser 102 instructions on where and how to orient device camera 130 tocapture the image of the instance. The instruction may be displayedthrough check-in application 112 or through camera application 120,including directional instructions, compass/navigational instructions,or visual instructions in a display interface of camera application 120,as will be explained in more detail herein. If user 102 chooses tocapture the image using the instructions, when the instance occurs,check-in application 112 may receive a command from one or more ofwireless beacons 146 to capture the image. The command may be issued bywireless beacons 146 simultaneously to all devices following theinstructions to capture the image. Thus, the command may enablesynchronized images/photography of an event. In other embodiments, therequest may include a countdown timer until the instance, therebyremoving the need to have a command sent by wireless beacons 146.Additionally, other requests/commands may utilize more than two steps,such as an initial request, a first command to capture a first image, asecond command to capture a second image, etc. Other embodiments mayutilize further requests/commands to update an initial request/commandbased on a new timer, time frame, and/or instance.

In other embodiments, wireless beacons 146 may issue a single command,as will be explained in more detail herein. Thus, check-in application112 may receive a single command to capture an image of an instanceduring an event. The command may occur at some time preceding theinstance or at the time of occurrence of the instance. The command mayinstead instruct camera application 120 and device camera 130 to capturean image of the instance. The command may also include additionalparameters, processes, or information, which may execute the commandonly if camera application 120 and device camera 130 are oriented tocapture the image of the instance. Thus, the command may utilize a map,compass, accelerometer, or other functions and devices of user device110 to determine if device camera 130 can capture the image. Therefore,if user 102 has pointed device camera 130 at the event to captureimages, the command may capture an image of the instance. Conversely, ifuser 102 has placed user device 110 away (e.g., in a pocket or case),the command may have no effect. Additionally, the request/command mayinclude a request/command to capture a single image, a plurality ofimages including a plurality of images at predetermined intervals, asound recording, and/or a video recording.

Camera application 120 may be configured to provide an application tocapture images using a device camera of user device 110, such as devicecamera 130. Camera application 120 may provide additionally processingafter capturing an image, including cropping, adjustingcolor/saturation/resolution, or other editing procedures. Cameraapplication 120 may utilize functions associated with device camera 130,such as flash, zoom, image resolution, or other camera parameter.Additionally, camera application 120 may provide for creating,accessing, and editing a library of images, such as a photo library ofcaptured images stored in database 116. The library and/or individualimages may be accessible by one or more other applications through anAPI of camera application 120. Images captured by device camera 130 maycorrespond to still images and/or video images.

As previously discussed, camera application 120 may receiverequests/commands to capture images from check-in application 112.Camera application 120 may therefore process the requests/commands andcapture an image of an instance. Additionally, the requests/commands maylock and unlock camera application 120, as previously discussed. Oncethe request/command is received, camera application 120 may displayinstructions to user 102 if the instructions are included in thecommand/request. The instruction may include word, directional, orvisual instructions. Directional instruction may include areas/locationsin venue 140, cardinal directions, up/down/right/left direction, cameratilt, etc. Visual instructions displayed to user 102 in cameraapplication 120 may include points, dots, circles, boxes, and/orhighlights of certain areas, people, things, or other area in the imageimage

Although for purposes of clarity the requests/commands are discussed andissuing a request/command to capture an image of the instance, in otherembodiments, different media may be captured by the request/command. Forexample, media may comprise still images, audio recordings, videorecords, and/or other audiovisual media recordings. Thus, arequest/command to capture media of the instance may comprise arequest/command to capture a still image, an audio recording, a videorecording, or other audiovisual data and/or information of the instanceduring the event. Additionally, the request/command may comprise arequest/command to generally capture media (e.g., a media types chosenby user 102) or capture a plurality of media types (e.g., a still imageand a video recording).

The image may be displayed to user 102 after the image is captured. User102 may then choose to upload the image to image processing server 150,save the image locally to database 116, or delete the image. If user 102chooses to upload the image to image processing server 150, the imagemay be utilized to construct an interactive scene of the instance duringthe event at venue 140, as will be explained in more detail herein. User102 may utilize camera application 120 or a browser application of userdevice 110 to view and/or navigate the interactive scene.

Device camera 130 corresponds to an optical device of user device 110enabling user 102 to record images, including still and/or video images.Device camera 130 may correspond to a digital camera on a user device,or may more generally correspond to any device capable of recording animage. Device camera 130 may include various features, such as zoom,flash, focus correction, shutter speed controls, or other variousfeatures usable to capture one or more images. Device camera 130 mayfurther display a preview and/or captured image to user 102 throughanother device of user device 110, such as a viewfinder, screen (e.g.,mobile phone screen), display interface of camera application 120, orother display. User 102 may utilize device camera 130 with cameraapplication 120 to record still images and/or video images.

In various embodiments, one or more features of check-in application 112and/or camera application 120 may be incorporated in the sameapplication so as to provide their respective features in oneapplication.

User device 110 includes other applications 114 as may be desired inparticular embodiments to provide features to user device 110. Forexample, other applications 114 may include security applications forimplementing client-side security features, programmatic clientapplications for interfacing with appropriate application programminginterfaces (APIs) over network 160, or other types of applications.Other applications 114 may also include email, texting, voice and IMapplications that allow a user to send and receive emails, calls, texts,and other notifications through network 160. In various embodiments,other applications 114 may include financial applications, such asbanking, online payments, money transfer, or other applicationsassociated with image processing server 150. Other applications 114 mayinclude browser, social networking, mapping, navigational, compass,etc., applications standard to a mobile phone, tablet computer, wearablecomputing device, and/or personal computer, which may also be used inconjunction with check-in application 112 and/or camera application 120.Other applications 114 may contain software programs, executable by aprocessor, including a graphical user interface (GUI) configured toprovide an interface to the user.

User device 110 may further include database 116 which may include, forexample, identifiers such as operating system registry entries, cookiesassociated with check-in application 112, camera application 120, and/orother applications 114, identifiers associated with hardware of userdevice 110, or other appropriate identifiers, such as identifiers usedfor payment/user/device authentication or identification. Identifiers indatabase 116 may be used by a service provider, such as image processingserver 150, to associate user device 110 with a particular accountmaintained by the service provider or identify user 102 and/or userdevice 110 with image data submitted by user device 110. Database 116may include tokens and/or encryption keys, such as an encryption keycorresponding to one or more of wireless beacons 146, venue 140 (ordevices/servers for venue 140), and/or image processing server 150.Database 116 may include identifying information for tokens enablingcheck-in application 112 to identify wireless beacons 146, venue 140 (ordevices/servers for venue 140), and/or image processing server 150 whenreceiving a corresponding check-in token.

Requests/command to capture an image of an instance during an event atvenue 140 may be stored or written to database 116 as necessary. Forexample, the request/command may correspond to a future instance, wherethe request/command is stored with accompanying data until the instanceoccurs. The accompanying data may include a countdown to the instance,directional information for device camera 130, or other necessary dataincluding lockout data/commands for camera application 120 and devicecamera 130. Database 116 may further store images captured by devicecamera 130. Images in database 116 may include images for use by imageprocessing server 150 to create an interactive scene. Thus, user device110 may transmit images in database 116 to image processing server 150.

User device 110 includes at least one communication module 118 adaptedto communicate with wireless beacons 146 and/or image processing server150. In various embodiments, communication module 118 may include a DSL(e.g., Digital Subscriber Line) modem, a PSTN (Public Switched TelephoneNetwork) modem, an Ethernet device, a broadband device, a satellitedevice and/or various other types of wired and/or wireless networkcommunication devices including microwave, radio frequency, infrared,Bluetooth, and near field communication devices. Communication module118 may communicate directly with wireless beacons 146 using short rangecommunications, such as Bluetooth Low Energy, LTE Direct, radiofrequency, infrared, Bluetooth, WiFi, and near field communications.

Venue 140 may correspond to a physical location hosting or displaying anevent viewed by user 102. Venue 140 may correspond to a stadium, center(e.g., sports/convention center), theater/amphitheater, park, or otherlocation with an event may be offered to user 102. An event at venue 140may correspond to sports games, plays, speeches, theater, or otherplanned occasion. Venue 140 may include infrastructure for determiningif and when an instance may occur during the event and establishing aconnection or check-in with user device 110. For example, venue 140 mayinclude wireless beacons, computer systems including processing andmemory units, communication modules, and/or other necessaryinfrastructure. Thus, venue 140 of FIG. 1 contains an instancedetermination device 142 executing an instance determination application144 and wireless beacons 146. In other embodiments, venue 140 mayinclude additional or different hardware and infrastructure as required.

Instance determination device 142 may be implemented using anyappropriate hardware and software configured for wired and/or wirelesscommunication with wireless beacons 146 and/or image processing server150. For example, instance determination device 142 may be implementedas a personal computer (PC), a smart phone, laptop computer, wristwatchwith appropriate computer hardware resources, eyeglasses withappropriate computer hardware (e.g. GOOGLE GLASS®) and/or other types ofcomputing devices capable of transmitting and/or receiving data, such asan IPAD® from APPLE®. Instance determination device 142 may further haveconnected devices configured to receive input from an ongoing event oradministrator of an event. Such devices may include keyboards/mice,attached PC, tablet, or mobile phone computing devices, cameras, and/ormicrophones all configured to receive information. The information maybe utilized by instance determination application 144 to determine aninstance occurring during an event. Although a hardware device is shown,the device may be managed or controlled by any suitable processingdevice. Although only one device is shown, a plurality of devices mayfunction similarly. Moreover, in various embodiments, one or more of theapplications, processes, and/or features discussed below in reference toinstance determination device 142 may be included in image processingserver 150, and vice versa.

Instance determination device 142 of FIG. 1 executes instancedetermination application 144. Instance determination application 144may correspond to processes, procedures, and/or applications executableby a hardware processor, for example, a software program. In otherembodiments, instance determination device 142 may include additional ordifferent software as required.

Instance determination application 144 may be configured to determine ifand when an instance during an event may occur. Thus, instancedetermination application 144 may be configured to receive and collectinput from instance determination device 142 and process the input. Aspreviously discussed, the input may correspond to direct input from anadministrator of an event, such as a director of a play, announcer of asports game, etc., and thus note a time and location within venue 140for the instance. In such embodiments, the input may correspond totext/data input from the administrator.

In other embodiments, instance determination application 144 may receiveother input, such as data input from cameras, microphones, or otherinput/output devices of instance determination device 142. Such inputmay determine an upcoming instance to occur or the present occurrence ofan instance. For example, a camera may be utilized to determine if aplayer or musician has left the event and that the next player ormusician is soon to arrive. Thus, instance determination application 144may determine an instance is about to occur. In other embodiments, thecamera or a microphone may detect a play in a sports game has occurredor a musician is playing a specific song. Thus, instance determinationapplication 144 may determine an instance is presently occurring in theevent at venue 140.

Instance determination application 144 may process the input andgenerate a request/command to capture an image that is distributed touser device 110 using wireless beacons 146. As previously discussed, therequest/command may include a two part/phase initiation or only a singlecommand to capture the image. For example, if instance determinationapplication 144 determines an instance is going to occur and knows theexact or approximate time until the instance occurs, instancedetermination application 144 may issue a request to capture an image ofthe instance to wireless beacons 146 for distribution to user device110. The request may activate at the end of the time period and captureor attempt to capture the image. In certain embodiments, the request mayonly activate if certain parameters are met, such as an orientation ofdevice camera 130. However, in other embodiments, instance determinationapplication 144 may not know the exact timing of the future instance andthus utilize wireless beacons 146 to capture an image of the instancewhen the instance occurs using a second command, as determined byinstance determination device 142. Furthermore, instance determinationapplication 144 may receive input of the present occurrence of aninstance and issue a command for distribution by wireless beacons 146 tocapture the image of the instance. In both embodiments, the command maycapture or attempt to capture the image, or may only capture the imageif parameters are met, such as the orientation of device camera 130.

Instance determination device 142 may include a check-in application,which may correspond to processes to complete check-in with user device110 for venue 140 (e.g., with one or more of wireless beacons 146established at venue 140). Thus, the check-in application may correspondto an application configured to receive check-in information from userdevice 110 and complete the check-in. The check-in request may includelog in information for a user account with venue 140 and/or imageprocessing server 150 and thus complete the check-in with user 102 byverifying the account information. For example, the check-in informationmay include an identifier or other account information for a useraccount of user 102. However, in embodiments where a user account hasnot been previously established by user 102, the check-in applicationmay receive other information identifying user 102 and/or user device110, including a user name/identifier, user device identifier, anidentifier for an account with another server, or other information. Invarious embodiments, the check-in information does not need to beutilized to complete a check-in and may be utilized by wireless beacons146 to transmit a request/command to capture an image of an instanceduring an event at venue 140.

Wireless beacons 146 may be maintained, for example, by venue 140 and/orimage processing server 150. Wireless beacons 146 may be implementedusing any appropriate hardware and software configured for wirelesscommunication with user device 110. For example, in one embodiment, oneor more of wireless beacons 146 may be implemented as a dongle deviceincluding a hardware processor and a communication module, for example,connected to device at venue 140 (e.g., instance determination device142). Wireless beacons 146 may also be implemented as devicesincorporated within a personal computer (PC), a smart phone, laptopcomputer, and/or other types of computing devices capable oftransmitting and/or receiving data, such as an IPAD® from APPLE®.Wireless beacons 146 may also act as stand-alone devices including aprocessor, communication module, and/or network interface componentconfigured to communicate with user device 110 and/or instancedetermination device 142. Although wireless beacons 146 are described asa plurality of wireless beacons set up throughout venue 140, in variousembodiments, wireless beacons 146 may correspond to a single wirelessbeacon established at venue 140.

Each of wireless beacons 146 may be established in a specific spot invenue 140, such as various seating areas, parts of grandstands, etc. Forexample, one of wireless beacons 146 may be established on a bottomfloor level of a theater, another in a mezzanine area, and another on atop floor. Wireless beacons 146 of FIG. 1 contains processes,procedures, and/or applications executable by a hardware processor, forexample, a software program, configured to interact with user device 110and/or instance determination device 142. Thus, regardless of theimplementation of wireless beacons 146 as discussed above, each ofwireless beacons 146 may utilize a check-in process and include or beconnected to a communication module. In other embodiments, wirelessbeacons 146 may include additional or different software and devices asrequired.

Each of wireless beacons 146 may include an application for transmittingrequests to establish a connection between a device (e.g., user device110) and one of wireless beacons 146. The requests may be unique to eachof wireless beacons 146 and form a connection with only the matching oneof wireless beacons 146. In other embodiments, the request may be uniqueto a subset of wireless beacons 146 or shared by all of wireless beacons146. Thus, wireless beacons 146 may utilize short range wirelesscommunications of wireless beacons 146 to transmit the requests toestablish a connection, including an identifier such as a UniversallyUnique Identifier (UUID). If user device 110 receives a request toestablish the connection with wireless beacons 146 and responds with anidentifier for user 102/user device 110 (potentially including the UUIDand other information necessary to effectuate a check-in for user 102),wireless beacons 146 to ramp up in power and create a connection betweenuser device 110 and one of wireless beacons 146.

Each of wireless beacons 146 may uniquely transmit the request toestablish the connection with wireless beacons 146 as a short rangewireless communication (e.g. a BLE protocol communication) including a“wake up” process for check-in application 112 of user device 110 and/ora token for the one of wireless beacons 146 transmitting the request. Inother embodiments, the request and/or connection may utilize near fieldcommunication, radio communication, infrared communication, or Bluetoothcommunication. Additionally, although wireless beacons 146 may utilizeBLE protocol communications to effectuate an “always on” type servicewhere the UUID and “wake up” process are transmitted continuously, othercommunication protocols used to provide an “always on” service mayinclude QUALCOMM® LTE Direct or similar device-to-device communicationtechnology. BLE and LTE Direct may both be utilized to provide discoveryof nearby devices to wireless beacons 146 (e.g., user device 110 and/orvenue 140) and establishment of a connection for data transfers

The request may be specific to user device 110 by including informationthat is specific to user 102, such as a name, identifier, or user deviceidentifier. The information specific to user 102 may be determined froma user account of user 102 or other information previously provided tovenue 140 (or instance determination device 142) and/or image processingserver 150. Thus, in certain embodiments, only user device 110 will pickup and authenticate the request. In other embodiments, user device 110may only pick up the request based on the signal range and/or physicalcontext for one of wireless beacons 146 transmitting the request. Forexample, one of wireless beacons 146 established at an ordering intercommay be limited in range only to the first floor, mezzanine, top floor,infield/outfield seats, goal line/50 yard line seats, etc..

After one of wireless beacons 146 receives an identifier from userdevice 110, the one of wireless beacons 146 may determine user 102 is inproximity to itself. The beacon of wireless beacons 146 forming theconnection with user device 110 may keep the connection open betweenuser device 110 and the beacon, may transmit the identifier to instancedetermination device 142 and/or image processing server 150, or mayclose the connection. However, one wireless beacons 146 receive arequest/command to capture an image of an instance during an event atvenue 140, wireless beacons 146 may utilize the identifier and/orconnection with user device 110 to transmit the request/command to userdevice 110. In certain embodiments, wireless beacons 146 may receiveinformation from user device 110, including an opt out feature toprevent future requests/commands from instance determination device 142as well as images captured by user device 110 from a request/commandissued by wireless beacons 146. Wireless beacons 146 may also transmitfurther information to user device 110, including information to preventcamera application 120 and/or device camera 130 from operating, even ifuser device 110 requests to opt out from the image capturing service ofinstance determination device 142.

Each of wireless beacons 146 includes a communication module adapted tocommunicate with user device 110, instance determination device 142,and/or image processing server 150. The communication module may includea DSL (e.g., Digital Subscriber Line) modem, a PSTN (Public SwitchedTelephone Network) modem, an Ethernet device, a broadband device, asatellite device and/or various other types of wired and/or wirelessnetwork communication devices including microwave, radio frequency,infrared, Bluetooth, and near field communication devices. Thecommunication module may communicate with user device 110 and/orinstance determination device 142 using short range communications, suchas Bluetooth Low Energy, LTE Direct, radio frequency, infrared,Bluetooth, and near field communications.

Image processing server 150 may be maintained, for example, by an onlineservice provider, which may provide image processing services andinteractive scene construction to user 102. In this regard, imageprocessing server 150 includes one or more processing applications whichmay be configured to interact with user device 110, wireless beacons146, and/or venue 140 to facilitate the generation of an interactivescene. In one example, image processing server 150 may be provided bySTUBHUB®, Inc. of San Francisco, Calif., USA. However, in otherembodiments, image processing server 150 may be maintained by or includean image, photograph, social networking, or other server that mayprovide image processing and hosting services to user 102 and/or venue140. Moreover, in various embodiments, one or more of the applications,processes, and/or features discussed below in reference to imageprocessing server 150 may be included in venue 140, and vice versa.

Image processing server 150 of FIG. 1 includes an image processingapplication 152, other applications 154, a database 156, and a networkinterface component 158. Image processing application 152 and otherapplications 154 may correspond to processes, procedures, and/orapplications executable by a hardware processor, for example, a softwareprogram. In other embodiments, image processing server 150 may includeadditional or different software as required, such as a check-inapplication as discussed in reference to venue 140, where those featuresare instead provided by image processing server 150.

Image processing application 152 may be configured to receiveinformation from and/or transmit information to user device 110 and/orinstance determination device 142 for processing and generation of aninteractive scene. Image processing application 152 may include one ormore applications to process image data from user device 110 and/orinstance determination device 142 by receiving the image data of aninstance during an event hosted at venue 140. Image data may be capturedafter an instance during an event occurs. The image data may correspondto one or a plurality of images captured at the same time (e.g., throughsynchronized image capturing, as previously discussed). The same timemay include images captured at approximately the same moment or within atime range, such as less than approximately 5 seconds, 4 seconds, orless. Thus, synchronized image data may include images of an instancecaptured within a time frame established in the request/command. Such atime frame may correspond to an issued time (e.g., 3:50:55 PM) or to acountdown timer (e.g., a 10 second timer). Thus, image processingapplication 152 may enable capture of media within the time frameoccurring surrounding the issued time or countdown timer. Once theimages are captured, either by user device 110, another device, and/orinstance determination device 142, the images may be uploaded forprocessing by image processing server 150.

Image processing application 152 may process the image data byassociating the image data with the uploading party and allowing users(including user 102) to view the image data. The image data may becollected to correspond to the same instance or event that was capturedin the image data. Thus, users may be enabled to view image data for avariety of perspectives and audience members of the instance in theevent. The image data may also be associated with a user account for theuploading user so that the uploading user may view the image datathrough accessing the user account.

In various embodiments, image processing application 152 may furthergenerate an interactive scene using the image data. An interactive scenemay correspond to a scene of the instance captured by the plurality ofimages in the image data during the event. The interactive scene mayenable user 102 to browse, scroll, navigate, pan, and/or rotate views ofthe instance using the image data. Thus, user 102 may interact with theimage data to view the instance through the synchronized images. Imageprocessing application 152 has generated the interactive scene, imageprocessing application 152 may allow user 102 to access the interactivescene or may transmit the interactive scene to user device 110 forviewing by user 102.

In various embodiments, image processing server 150 includes otherapplications 154 as may be desired in particular embodiments to providefeatures to image processing server 150. For example, other applications154 may include security applications for implementing server-sidesecurity features, programmatic server applications for interfacing withappropriate application programming interfaces (APIs) over network 160,or other types of applications. Other applications 154 may containsoftware programs, executable by a processor, including a graphical userinterface (GUI), configured to provide an interface to a user.

Additionally, image processing server 150 includes database 156. Aspreviously discussed, user 102 and/or merchant 104 may establish one ormore user accounts with image processing server 150. User accounts indatabase 156 may include user information, such as name, address,birthdate, payment/funding information, and/or other desired user data,as well as image data from images captured by user device 110 and/orinstance determination device 142. User accounts in database 156 mayalso be associated with interactive scenes constructed from thoseimages. User 102 may link to their respective user accounts through anidentifier. Thus, when the identifier is transmitted to image processingserver 150, a user account belonging to user 102 may be found. Once auser account is found, image data and interactive scenes associated withthe user account may be retrieved for user 102. In other embodiments,user 102 and/or merchant 104 may not have previously established anaccount and may provide other identifiers or information, as previouslydiscussed, to find and retrieve image data and interactive scenes.

In various embodiments, image processing server 150 includes at leastone network interface component 158 adapted to communicate user device110, instance determination device 142, and/or wireless beacons 146 overnetwork 160. In various embodiments, network interface component 158 maycomprise a DSL (e.g., Digital Subscriber Line) modem, a PSTN (PublicSwitched Telephone Network) modem, an Ethernet device, a broadbanddevice, a satellite device and/or various other types of wired and/orwireless network communication devices including microwave, radiofrequency (RF), and infrared (IR) communication devices.

Network 160 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 160 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks. Thus,network 160 may correspond to small scale communication networks, suchas a private or local area network, or a larger scale network, such as awide area network or the Internet, accessible by the various componentsof system 100.

FIG. 2 is an exemplary environment including a plurality of userscapturing synchronized media of an instance during an event for usecreating an interactive scene, according to an embodiment. Environment200 of FIG. 2 includes a user 202 a operating a user device 210 a, auser 202 b operating a user device 210 b, and a user 202 c operating auser device 210 c all corresponding generally to user 102 operating userdevice 110 of FIG. 1. Environment 200 further includes a wireless beacon246 a, a wireless beacon 246 b, and a wireless beacon 246 c allcorresponding generally to wireless beacons 146 of FIG. 1. Moreover, avenue 240, corresponding generally to venue 140 of FIG. 1, includes aninstance determination device 242 a, an instance determination device242 b, and an instance determination device 242 c all correspondinggenerally to instance determination device 142 of FIG. 1.

Environment 200 includes venue 240 hosting an event 270 viewed by user202 a, 202 b, and 202 c. As previously discussed, event 270 maycorrespond to a concert sports game, exhibit, public gathering, speech,etc. Thus, user 202 a, 202 b, and 202 c are viewing event 270 atdifferent locations in venue 240. For example, event 270 may correspondto a football game where user 202 a views the football game from one setof seats, user 202 b another set of seats, and user 202 c a third set ofseats. Additionally, venue 240 includes instance determination devices242 a, 242 b, and 242 c set up to monitor event 270 and determine if andwhen an instance during event 270 may occur. For example, instancedetermination devices 242 a, 242 b, and 242 c may correspond to aplurality of optical cameras and microphones with backend processingequipment that may capture event 270 and determine if an instance duringevent 270 occurs or is going to occur. Instance determination devices242 a, 242 b, and 242 c may do so through audio, video, or audiovisualinput of event 270, input from a producer, administrator, or otherentity monitoring event 270, or through other information, as previouslydiscussed. Once instance determination devices 242 a, 242 b, and 242 cdetermine an instance is occurring or is going to occur, instancedetermination devices 242 a, 242 b, and 242 c may generate arequest/command to capture an image of the instance that may bedistributed to user devices 210 a, 210 b, and 210 c using wirelessbeacons 246 a, 246 b, and 246 c. The request/command may synchronizeuser device 210 a, 210 b, and 210 c to capture an image of the instancesimultaneously using their respective device cameras.

Thus, wireless beacons 246 a, 246 b, and 246 c may previously establisha connection with user devices 210 a, 210 b, and 210 c, respectively,when user device 210 a, 210 b, and 210 c, respectively, come in to rangeof the wireless beacons. Using the check-in information, or otherinformation provided by user device 210 a, 210 b, and 210 c to establishthe connection, wireless beacons 246 a, 246 b, and 246 c may distributethe request/command generated by instance determination devices 242 a,242 b, and 242 c. Since the request/command may synchronize user device210 a, 210 b, and 210 c to capture images of the instancesimultaneously, user devices 210 a, 210 b, and 210 c may process therequest/command and utilize device cameras to capture synchronizedimages of the instance. Once the images are captured, the images may beuploaded to an image processing server on approval by users 202 a, 202b, and 202 c, as previously discussed.

FIG. 3 is an exemplary system environment including a server preparingan interactive scene from synchronized media submitted by user devices,according to an embodiment. Environment 300 includes a user device 310and an image processing server 350 corresponding generally to userdevice 110 and image processing server 150, respectively, of FIG. 1.

Image processing server 350 may receive the image data uploaded fromuser devices (e.g., user device 310) after the image data is captured ofan instance during an event. Image processing server 350 executes animage processing application 352 corresponding generally to theprocesses and procedures discussed in reference to image processingapplication 152 of FIG. 1. Image processing application 352 utilizesevent 370 data having an event instance 372, a camera orientation 374,and an occurrence 376 with image data 380 having images 382 andinteractive scene 384. Event 370 data may correspond to data receivedfrom a venue's instance determination device(s) that may include theinformation for instances that occurred during the event and informationnecessary to construct an interactive scene from image data captured ofthe instance. Thus, event 370 data includes event instance 372 havingdata about the instance that occurred during the event. For example,event instance 372 may include an identifier and data for when a playoccurred during a sports game, a song or artist that performed during aconcert, or other instance that occurred during an event. Coupled withevent instance 372 data is camera orientation 374 data havinginformation about how and where a camera should be oriented to capturethe image. Camera orientation 374 may be utilized to build aninteractive scene and remove image data that does not correspond tocamera orientation, for example, if image data is received but aimed atthe audience of the event and not the instance in the event.Furthermore, occurrence 376 data includes information of when eventinstance 372 occurred, where event instance 372 occurred, and otherinformation to insure that all of the image data collected for eventinstance 372 is synchronized.

Image processing application 352 may utilize event 370 data with imagedata 380. Image data 380 includes images 382 that are uploaded to imageprocessing server 350 by user devices. Images 382 may correspond to theimage data for an event, and may be filtered using event 370 data toselect image data for only event instance 372. Once the image data forevent instance 382 is gathered from images 382, image processingapplication 352 may associate and/or process the image data for eventinstance 382 into an interactive scene 384 for event instance 372. Aspreviously discussed, interactive scene 384 may display all the imagescaptured simultaneously for event instance 372 and may be constructed toallow a user to browse, scroll, pan, rotate, etc. the images of thescene.

Once interactive scene 384 is constructed, user device 310 may access orreceive the interactive scene for display to a user (not shown) of userdevice 310. User device 310 displays a camera application interface 320corresponding generally to the processes and features described inreference to camera application 120 of FIG. 1. Camera applicationinterface 320 may display images 322, which may correspond to imagescaptured of interactive scene 384. Thus, images 322 include an image 324a, an image 324 b, an image 324 c, and an image 324 d. Images 322 maycorrespond to images of event instance 372 from interactive scene 384that may be taken from different devices when the images for eventinstance 372 was captured. Thus, the user is able to view images 322 ofevent instance 372 from a multitude of angles and perspectives. Furthercamera application interface 320 displays an interactive scene 326 ofevent instance 372 that is constructed to enable the user to navigatethrough images 322. Interactive scene 326 includes navigation tools toenable the user to move seamlessly through the scene and the differentperspectives. Thus, selection of pan 328 a and pan 328 b may enable theuser to move a camera perspective of event instance 372 left and right,respectively. Furthermore, selection of up 328 c and down 328 d mayenable the user to move the camera perspective up and down,respectively. The user is also enabled to rotate the scene to view thescene from different angles and sides using rotate 328 e and rotate 328f. Additional navigation tools may also be included in furtherembodiments.

FIG. 4 is a flowchart of an exemplary process for synchronized mediacapturing for an interactive scene, according to an embodiment. Notethat one or more steps, processes, and methods described herein may beomitted, performed in a different sequence, or combined as desired orappropriate.

At step 402, an occurrence of an instance during an event is determined.For example, it may be determined that an instance is or will occurduring the event. Additionally, it may be desirable to capture an imageof the instance, which may be an action during the event. The instancemay comprise a play in a sports game, a song or performance in aconcert, or an action in a stage performance. For example, during a goldtournament, an instance may correspond to the moment a golf ball isstruck. The moment the golf ball is struck may be determined usingmicrophone to pick up the sound of the contact between the golf club andthe golf ball. Thus, it may be determined that an instance has occurredusing the microphones and/or video cameras monitoring the players golfswing. Other instance may be determined using a schedule for upcomingartists in a concert, microphones detecting a note or series of notes ofa song (e.g., an audio sampling of the song), facial or otherrecognition and image processing, etc.

Check-in information for a device connected to a wireless beacon isaccessed, at step 404. The device and the wireless beacon may connectusing one of near field communication, radio communication, infraredcommunication, Bluetooth communication, Bluetooth Low Energy (BLE)communication, and LTE Direct communication. The device may alsocorrespond to a plurality of devices, such as a plurality of mobiledevices having a plurality of device cameras used to capture an image ofthe instance. Additionally, the wireless beacon may correspond to aplurality of wireless beacons set up throughout a venue. Thus, aplurality of connections between the plurality of devices and theplurality of wireless beacons may also be used.

At step 406, a command to capture an image of the instance is issued tothe device using the wireless beacon and the check-in information whenthe instance occurs. The command may also correspond to a request tocapture a future image of an upcoming instance. The request/command mayprevent the device from capturing images prior to the occurrence of theinstance. If the instance does not occur, the devices may be allowed toagain begin capturing images through a timer, countdown, instruction,etc. The request/command may also include a directional instruction foraiming the device to capture the image.

If the wireless beacon issues a request to capture a future image of aninstance that will occur, an occurrence of the instance may be detectedand a command to capture the image may be communicated to the devicebased on detecting the occurrence of the instance. In other embodiments,a timer or countdown may be used to trigger image capturing on theoccurrence of an instance. Additionally, it may be desired to capture asecond image of a second occurrence. Thus, another request/command maybe communicated to the device to capture the second image. Once theimage is captured, the image may be displayed to the user for the userto decide to upload to an image processing entity or to delete.

If the user chooses to upload the image, the image and/or image data maybe received, at step 408. The image and/or image data may be utilizedwith additional images and/or image data to construct an interactivescene of the instance. The interactive scene may be communicated to thedevice for the user to view. Additionally, the user may navigate theinteractive scene using the device.

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment. In variousembodiments, the user device may comprise a personal computing device(e.g., smart phone, a computing tablet, a personal computer, laptop, awearable computing device such as glasses or a watch, Bluetooth device,key FOB, badge, etc.) capable of communicating with the network. Theservice provider may utilize a network computing device (e.g., a networkserver) capable of communicating with the network. It should beappreciated that each of the devices utilized by users and serviceproviders may be implemented as computer system 500 in a manner asfollows.

Computer system 500 includes a bus 502 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 500. Components include aninput/output (I/O) component 504 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons,image, or links, and/or moving one or more images, etc., and sends acorresponding signal to bus 502. I/O component 504 may also include anoutput component, such as a display 511 and a cursor control 513 (suchas a keyboard, keypad, mouse, etc.). An optional audio input/outputcomponent 505 may also be included to allow a user to use voice forinputting information by converting audio signals. Audio I/O component505 may allow the user to hear audio. A transceiver or network interface506 transmits and receives signals between computer system 500 and otherdevices, such as another user device, service device, or a serviceprovider server via network 160. In one embodiment, the transmission iswireless, although other transmission mediums and methods may also besuitable. One or more processors 512, which can be a micro-controller,digital signal processor (DSP), or other processing component, processesthese various signals, such as for display on computer system 500 ortransmission to other devices via a communication link 518. Processor(s)512 may also control transmission of information, such as cookies or IPaddresses, to other devices.

Components of computer system 500 also include a system memory component514 (e.g., RAM), a static storage component 516 (e.g., ROM), and/or adisk drive 517. Computer system 500 performs specific operations byprocessor(s) 512 and other components by executing one or more sequencesof instructions contained in system memory component 514. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor(s) 512 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious embodiments, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 514, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 502. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled bycommunication link 518 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A system comprising: a non-transitory memorystoring check-in information for a plurality of devices; and one or morehardware processors in communication with the non-transitory memory andconfigured to; determine an occurrence of an instance in an event;access the check-in information for the plurality of devices connectedto at least one wireless beacon; communicate, using the at least onewireless beacon, a command to capture media of the instance to each ofthe plurality of devices using the check-in information when theinstance occurs; and receive a plurality of media data of the instancefrom the plurality of devices, wherein the plurality of media datacorresponds to the media captured by each of the plurality of devices.2. The system of claim 1, wherein the plurality of devices and the atleast one wireless beacon connect using one of near field communication,radio communication, infrared communication, Bluetooth communication,Bluetooth Low Energy (BLE) communication, WiFi communication, and LTEDirect communication.
 3. The system of claim 1, wherein the plurality ofdevices comprises a plurality of mobile devices, and wherein the commandutilizes a device camera on each of the plurality of mobile devices tocapture the media.
 4. The system of claim 1, wherein the one or morehardware processors are further configured to: construct an interactivescene of the instance using the plurality of media data.
 5. The systemof claim 4, wherein the one or more hardware processors are furtherconfigured to: communicate the interactive scene to at least one of theplurality of devices.
 6. The system of claim 5, wherein a user of the atleast one of the plurality of devices navigates the interactive sceneusing the at least one of the plurality of devices.
 7. The system ofclaim 1, wherein prior to the determining the occurrence of theinstance, the one or more hardware processors are further configured to:prevent each of the plurality of devices from capturing media prior tothe occurrence of the instance.
 8. The system of claim 7, wherein theone or more hardware processors are further configured to: allow each ofthe plurality of devices to capture the media if the instance does notoccur.
 9. The system of claim 1, wherein the command comprises adirectional instruction for aiming the device to a user for each of theplurality of devices.
 10. A method comprising: determining a firstinstance in an event for capturing first media of the first instance;accessing check-in information for a device based on a connectionbetween the device and a wireless beacon; communicating, using thewireless beacon, a request to capture the first media of the firstinstance to the device using the check-in information.
 11. The method ofclaim 10, wherein the first instance comprises one of a play in a sportsgame, a song or performance in a concert, and an action in a stageperformance.
 12. The method of claim 10 further comprising: detecting anoccurrence of the first instance; and communicating a command to capturethe first media based on the detecting the occurrence of the firstinstance.
 13. The method of claim 10, wherein the first media isdisplayed to a user of the device after the device captures the firstmedia, and wherein the user chooses to transmit or delete the firstmedia.
 14. The method of claim 13 further comprising: determining asecond instance in the event for capturing second media of the secondinstance; and communicating, using the wireless beacon, a second requestto capture the second media of the second instance to the device usingthe check-in information.
 15. The method of claim 13 further comprising:receiving the first media of the first instance from the device when theuser chooses to transmit the first media.
 16. The method of claim 10,wherein the first request prevents the device from utilizing a camerauntil the device captures the first media.
 17. The method of claim 10,wherein the first request comprises a directional instruction for aiminga camera of the device to a user for the device.
 18. A non-transitorycomputer-readable medium comprising instructions which, in response toexecution by a computer system, cause the computer system to perform amethod comprising: determining an instance in an event; accessing thecheck-in information for the plurality of devices connected to at leastone wireless beacon; and issuing, using the at least one wirelessbeacon, a command to capture media of the instance to the plurality ofdevices using the check-in information when the instance occurs.
 19. Thenon-transitory computer-readable medium of claim 18, wherein the commandprevents the plurality of devices from utilizing a camera until theplurality of devices captures the media.
 20. The non-transitorycomputer-readable medium of claim 18, wherein the media is displayed toa user of each of the plurality of devices after the plurality ofdevices captures the media, and wherein the user chooses to transmit ordelete the media.